|
The slow programming movement is part of the slow movement. It is a software development philosophy that emphasises careful design, quality code, software testing and thinking. It strives to avoid kludges, buggy code, and overly quick release cycles. Overly quick release cycles can prevent programmers from taking the time to write proper code, think through designs, and get enough rest for them to work effectively; there have been reports of overworked software teams actually losing ground by working extra hours. Due to exhaustion, the programmers introduce more bugs into their code than they can fix.〔Robinson. 2012. http://www.salon.com/2012/03/14/bring_back_the_40_hour_work_week/〕 ==External links== * (How NOT to go about a programming assignment ) An ironic description of a 'fast programming' paradigm * (Teach Yourself Programming in Ten Years ) An essay on developing expertise in programming, by Peter Norvig * (Technical Debt ) Technical Debt, by Martin Fowler * (Top Ten Idea Killers in Software Development ) Top Ten Idea Killers in Software Development, by Navneeth Mandavilli * () Fragile Manifesto 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「Slow programming」の詳細全文を読む スポンサード リンク
|